This adds a new Trait called GazeLockControl

The idea is it extends the functionality of the plugin so you easily see if the current user is the controlling user and define what is hidden in your pages etc based on that logic.

This isn't forced etc, so is up to the user to implement if they want the logic.

For example, take the below, I have an Edit Customer page, where I only want users controlling the page to have the ability to save / delete.

This is something I also saw via #26 so thought I'd give it a whirl at implementing.

Below is an example of how it works in this use case - for example an Edit page:

class EditCustomer extends EditRecord
{
    use GazeLockControl;

    protected static string $resource = CustomerResource::class;

    protected function getHeaderActions(): array
    {
        return [
            Actions\DeleteAction::make()->hidden(!$this->hasGazeControl()),
        ];
    }

    protected function getFormActions(): array
    {
        return [
            Actions\Action::make('Save')->action('save')->hidden(!$this->hasGazeControl()),
        ];
    }
}

Here's a Loom of how it works also:
https://www.loom.com/share/f8c66721ff934ea8bba86be8d39af7bc?sid=21cb0f9c-8eb1-47ba-a18b-b6ffe446939c

Let me know if there's any adjustments needed 👍🏻